Loading TOC...

PUT /manage/v2/databases/{id|name}/alert/configs/properties

Summary

This resource address updates the configuration properties of the alert specified by the mandatory uri parameter from the specified database.

URL Parameters
uri The URI of the alert. This parameter is required.
format The format of the posted data. Can be either json or xml (default). This value overrides the Accept header if both are present.
Request Headers
Accept The expected MIME type of the request body. If the format? parameter is present, it takes precedence over the Accept header.
Content-type The MIME type of the data in the request body. Depending upon the value of the format parameter or Accept header, one of application/xml, application/json, or text/html.
Response Headers
Content-type The MIME type of the data in the response body. Depending upon the value of the format parameter or Accept header, one of application/xml, application/json, or text/html.

Response

Upon success, MarkLogic Server returns a status code 202 (Accepted) if the request causes a restart, or status code 204 (No Content) if the request does not cause a restart. If the payload is malformed or the alert does not exist, a status code of 400 (Bad Request) is returned. A status code of 401 (Unauthorized) is returned if the user does not have the necessary privileges.

Required Privileges

This operation requires one of the following:

Usage Notes

The properties that can be modified are listed below.

Note: The properties described here are for XML payloads. In general they are the same for JSON, with the exception that, in JSON, schemas, namespaces, using-namespaces, module-locations, events, audit-events, and audit-restrictions are expressed in singular form.

id

uri

name

description

triggers

The triggers for an alert configuration.

This is a complex structure with the following children:

trigger

domains

The cpf domains for an alert configuration.

This is a complex structure with the following children:

domain

options

This is a complex structure with the following children:

option

actions

This is a complex structure with the following children:

action

Example


curl -X PUT --digest -u admin:admin -H "Content-type: application/json" \
-d '{  
    "name": "New Name",
    "description": "New Description"
   }' \
http://localhost:8002/manage/v2/databases/Documents/alert/configs/properties?uri=my-alert-config

==>  Updates the "name" and "description" properties of the "my-alert-config" alert.

Stack Overflow iconStack Overflow: Get the most useful answers to questions from the MarkLogic community, or ask your own question.